UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The IDPS must capture and log organizationally defined additional information (identified by type, location, or subject) to the audit records for audit events.


Overview

Finding ID Version Rule ID IA Controls Severity
V-34546 SRG-NET-000080-IDPS-00065 SV-45388r1_rule Low
Description
Audit record content that may be necessary to satisfy this requirement includes timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. This capability is critical for accurate forensic analysis.
STIG Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide 2012-11-19

Details

Check Text ( C-42737r1_chk )
If the organization does not require organizationally defined additional information to be captured in the audit log from the IDPS, this is not a finding.
Examine the audit log configuration on the IDPS components (including the sensors) or view several alert records on organization's central audit log server.
Verify the entries sent to the audit log include organizationally defined additional information.

If the audit log event records do not include organizationally defined additional information, this is a finding.
Fix Text (F-38785r1_fix)
Configure the IDPS components, to ensure entries sent to the audit log include organizationally defined additional information. Organizational requirements for what audit events are required may be defined by type, location, or subject.